update description

the indenting in the test code is weird, should be two spaces and line up correctly.

i am not convinced this logic is correct. e.g. don't think the assert(value) form is accounted for? Maybe a better approach is to see if the argument named "message" is provided. (all the assert type definitions use message as the argument name). that should be available somehow.

I think we need a pass/fail test for every method https://nodejs.org/api/assert.html.

I was using @typescript-eslint/utils; somehow all the arguments are of type: 'Literal' argument and argument named ‘message’ is not available. Should we follow approach to load all assert methods in runtime from node:assert and get all the arguments length and then report back if arguments length are less than expected?

it should be possible to do along the lines of sth like:

          const parserServices = ESLintUtils.getParserServices(context);
          const checker = parserServices.program.getTypeChecker();
          const tsNode = parserServices.esTreeNodeToTSNodeMap.get(node);
          const signature = checker.getResolvedSignature(tsNode); /*?*/
          const messageParameterIndex = signature?.getParameters().findIndex((param) => param.name === 'message'); /*?*/

but we probably need to pay attention of performance impact, it's better to somehow cache those information rather the analyzing for each assertion if we do want to go down this path.

We can refactor to cache instead of analyzing each assertion to improve performance. Added valid test cases for assert.ifError that doesn't have message